home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr11
/
pdox693.zip
/
TI618.ASC
< prev
next >
Wrap
Text File
|
1993-02-23
|
8KB
|
265 lines
PRODUCT : Paradox NUMBER : 618
VERSION : 3.0 & up
OS : DOS
DATE : February 23, 1993 PAGE : 1/4
TITLE : Network Installation Overview
These notes are applicable to any Network using Paradox.
-----------------------------------------------------------------
You must create and map/link 3 special directories:
1) Paradox system file directory
2) Data file directory
3) User Private directory
┌───────────────────────────────────────────────────────────────┐
│1) \Pdox40, \Pdox35, \Paradox3 ▒ After installed, give │
│ minimum read, open, │
│ search rights │
│ │
│°Program Files │
│°Custom.sc and Custom.lib │
│ │
├───────────────────────────────────────────────────────────────┤
│2) \Pdoxdata Name is optional, could be any directory. Do not │
│ make \Pdoxdata a subdirectory of the system dir. │
│ ▒ Give all rights - │
│ read, write, create, │
│°Shared User Data delete. Parental not │
│°Pdoxusrs\Paradox.Net necessary (for the │
│ || creation of │
│(Will be created as directories). │
│ first user loads Paradox) │
│(Controls sharing of data │
│ and serial numbers) │
├───────────────────────────────────────────────────────────────┤
│3) \Private ▒ Give all rights │
│ Can be local hard │
│ disk directory │
│°Each user needs unique Private dir │
│°Temp files - Answer ... │
│°Scratch/Sort files │
│°Paradox.CFG (Default printer, User Name, │
│ Private Dir Location) │
│ (First .CFG file found on path will be used!) │
└───────────────────────────────────────────────────────────────┘
PRODUCT : Paradox NUMBER : 618
VERSION : 3.0 & up
OS : DOS
DATE : February 23, 1993 PAGE : 2/4
TITLE : Network Installation Overview
Tips:
o Read the first two chapters of the Paradox Network
Administrator's Guide and the chapter on "Other" Networks.
In Paradox 4.0 you can read about network specific
instructions in the online text files specified in Table
2-1 of the Network Installation Guide.
o Start Paradox from the Private Directory.
o Have Paradox and the Private directories on the DOS PATH
with the Private directory appearing before Paradox.
o Do NOT make the \PDOXDATA directory a child directory of
the Paradox system directory (i.e. \PARADOX). On some
networks the child directory cannot have greater rights
than the parent.
o Have every user reference shared directories by the same
logical drive name (NOT C:\something).
o If on a non-dedicated network such as LANtastic, do not
let users work from the server via a physical drive name
such as C:, but rather make sure to work from the same
logical drives as the workstations, like E:.
o Create a PARADOX.CFG for each user as per Chapter 4
Network Installation Guide (if you are using Paradox 3.5,
see the Network Administrator's Guide chapter called
"Configuration").
o Once installed eliminate PARADOX.CFG from the Paradox
system file directory since each user will have their own
copy.
o On most Networks of type OTHER use -SHARE option to start
Paradox (Paradox -share). This will usually mean that you
have to invoke the DOS SHARE command as well.
o If you are using Paradox version 3, substitute "Paradox3"
where you read "Paradox" above.
PRODUCT : Paradox NUMBER : 618
VERSION : 3.0 & up
OS : DOS
DATE : February 23, 1993 PAGE : 3/4
TITLE : Network Installation Overview
Common Questions:
What are the causes for the message "Unable to record lock unlock
Pdoxusrs\Paradox.Net"?
o Insufficient rights in PDOXDATA directory.
o Linking or mapping statements do not match the location
specified at install time for the Pdoxusrs\Paradox.Net
(Run Nupdate.exe from the \Paradox directory or the
install disk to reset location, or redo network map or
link statements).
o Finding someone else's PARADOX.CFG file along PATH at
startup.
o Presence of a leftover *.lck file due to someone
abnormally exiting Paradox. (With no one in Paradox the
presence of a *.lck file indicates an earlier problem.
When no one is in Paradox you can delete any *.lck files
or even the Pdoxusrs\Paradox.Net file to start afresh).
Why the message "Not enough disk space to complete operation"?
o On networks, Paradox disk space requirements refer to the
User's PRIVATE directory. You need between 2 and 3 times
the size of free disk space available in the User's
PRIVATE directory for the tables in question. Use
Tools/Net/SetPrivate to test Private Directory location.
Is there a way around the message "Sharing Violation"?
o This message may occur with multiple users (or sessions
such as in Microsoft Windows) sharing the Paradox system
files. This message has been reported on Networks such as
Banyan's Vines and LANtastic from Artisoft. Another
symptom of the same problem is when a second session
cannot start Paradox.
o One method of getting beyond this message is to use the
DOS ATTRIB Command to set *.EXE Files within the Paradox
directory to READ ONLY (e.g. ATTRIB +R *.EXE from the
Paradox directory prompt).
PRODUCT : Paradox NUMBER : 618
VERSION : 3.0 & up
OS : DOS
DATE : February 23, 1993 PAGE : 4/4
TITLE : Network Installation Overview
The following Technical Information Sheets cover information
about running Paradox on a Network:
TI # Title
1246 Table Formats and Network Locking Protocol
1063 Paradox Table and Directory Locks
1109 Record Locks on a Network in Paradox 4.0
581 Installing Paradox on a LANtastic Network
158 Installing Paradox on Netware Lite
DISCLAIMER: You have the right to use this technical information
subject to the terms of the No-Nonsense License Statement that
you received with the Borland product to which this information
pertains.